@0B@ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
                   @0F@Welcome to the ViaSoft Support BBS@0B@
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

                    @0A@<Your introductory message here>@0B@


ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
            @0F@ViaMAIL! - Fully Integrated Mailer for WILDCAT! v4@0B@
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ@0E@
Human caller detected.  Loading the BBS, please wait...
Press [ESC] twice to load the BBS...

Time expired, loading BBS...

[ESC] pressed.  Loading BBS, please wait...

Minimum baud rate of 1200 baud required during this time frame.

Minimum 2400 baud rate connection required.

Minimum 4800 baud rate connection required.

Minimum 7200 baud rate connection required.

Minimum 9600 baud rate connection required.

Minimum 12000 baud rate connection required.

Minimum 14400 baud rate connection required.

Minimum 16800 baud rate connection required.

Minimum 19200 baud rate connection required.

Minimum 21600 baud rate connection required.

Minimum 24000 baud rate connection required.

Minimum 26400 baud rate connection required.

Minimum 28800 baud rate connection required.

Minimum 31200 baud rate connection required.

Minimum 33600 baud rate connection required.

Minimum 38400 baud rate connection required.

Minimum 57600 baud rate connection required.

Minimum 115200 baud rate connection required.

During the current event, only calls from other systems to transfer mail
will be accepted.  Unfortunately, you'll need to try back later.

During the current event, only calls from humans will be accepted.  To
determine the best time to transfer mail, you should contact the SysOp of
this system for further information.
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
             A U T O M A T E D    R E S P O N S E    M E S S A G E
                           FileRequest/ViaSERV! v1
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  In response to your request for file(s), the following action(s) have
  taken place:



  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
                            End of Response Message
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
             A U T O M A T E D    R E S P O N S E    M E S S A G E
                           FileRequest/ViaSERV! v1
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  FileRequests are not allowed during the current event.  Please try your
  request later.



  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
                            End of Response Message
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
             A U T O M A T E D    R E S P O N S E    M E S S A G E
                                 ViaSERV!
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ


  Your address (listed above) is not known to this system and as a result,
  you will not be able to utilize the automated commands of ViaSERV!.

  If you feel you're receiving this message in error, please contact the
  SysOp of this system for further information.  For your convenience,
  information on using ViaSERV! follows.


  According to this systems present configuration, your address (listed
  above) has been prohibited from using the ViaSERV! functions.

  If you feel you're receiving this message in error, please contact the
  SysOp of this system for additional information.  Unfortunately, no
  further action from the request message is being taken.

  According to this systems present configuration, the password used
  on the subject line doesn't match the one defined for your address.

  If you feel you're receiving this message in error, please contact the
  SysOp of this system for additional information.  Unfortunately, no
  further action from the request message is being taken.


  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
                             End of Response Message
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
                           Continued in Next Message
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
             A U T O M A T E D    R E S P O N S E    M E S S A G E
                             ViaSERV! - Continued
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
                      H E L P   I N F O R M A T I O N
                            Revised: 05/06/96
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  This system uses a special command interpreter (called ViaSERV!) which
  allows you to send specially formatted netmail messages addressed to the
  appropriate server and upon validation of the command(s), perform
  changes to your configuration.  This process is completely automatic and
  requires little (if any) intervention on the local system administrators
  part.


  COMMAND SERVER
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  Presently two server names are used:

                     ECHOSERV - Echomail conferences
                     ARCSERV  - Filebone conferences

  Selecting the apropriate server name only affects the performance of the
  SUBSCRIBE and UNSUBSCRIBE commands.  For example, using ECHOSERV in the
  To: name field dictates that using either the SUB/UNSUB commands will
  only affect the echomail conferences.  Likewise, using ARCSERV will only
  affect your filebone or TIC file areas.

  Since a common command set is used, you may take advantage of the various
  SET and GET commands (such as changing passwords, compression methods
  etc) regardless of which server the message is actually addressed to.
  This greatly simplies things by preventing you from having to learn a
  second set of commands.


  SECURITY
  ÄÄÄÄÄÄÄÄ

  Due to the power of this capability, ViaSERV! employs built-in security
  methods preventing unauthorized systems from gaining access and altering
  your configuration.  Any attempts to activate options you don't have
  sufficient access to will produce a response message back to your system
  informing you of this.

  All security level definitions and configuration is handled at the
  uplinks system, so any changes with regard to security must be made
  directly by the uplinks SysOp.  If you have any questions in this regard,
  you should contact him/her directly.


  RESPONSE MESSAGE
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  For every message you send, you will receive a response back telling you
  what was the outcome of the commands used.  Not only is this useful to
  verify that changes took place, but issuing the various GET STATUS, GET
  QUERY commands, you can see what are the conferences selected, your
  configuration and so on.


  SPECIALLY FORMATTED NETMAIL MESSAGE
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  When defining this message there's two distinct sections to configure.
  The message header (to/from addressing etc) and the message body.

  The message header selects the appropriate command server (ECHOSERV or
  ARCSERV) as well as the associated AKA address. The message body is
  where all the commands are placed.

  As mentioned above, selecting the To: name as ECHOSERV means using the
  SUB/UNSUB commands only affect your echomail areas and the name ARCSERV
  will only change your filebone or TIC file areas.


  MESSAGE HEADER
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  When defining the message header, the 5 basic sections are described
  below.

  To: address    The netmail message should be addressed to your uplinks
                 primary or any one of his AKAs (alternate addresses).

  To: name       Either ECHOSERV or ARCSERV.

  From: address  The FROM: address of the message should be your address
                 that has access to the related functions this request
                 is being configured for.  In other words, you should use
                 your correct AKA address relative to the network you're
                 requesting conferences for.  You wouldn't want to use
                 your Fido address for conferences within WSNET, instead
                 you would use your WSNET address.

  From: name     Normally you would use your regular name here.  This
                 field is not used except for display purposes.

  Subject line   This is one of the most crucial definitions because here
                 is where you specify your password that will enable the
                 use of the ViaSERV! commands.


  MESSAGE BODY
  ÄÄÄÄÄÄÄÄÄÄÄÄ

  The message body portion of the Netmail message is where all the 'action'
  takes place.  Here you could use the various SET and GET type commands to
  perform the desired action.

  You should only use one SET or GET command per line along with it's
  apropriate parameters.  If you'd like to enter multiple commands, you may
  do so by using multiple lines (one command per line).

  Blank lines, that is, a line with no text on it as well as lines that
  start off with a ';' or '#' character (in position 1) will be ignored.
  You might structure your message this way to provide better formatting
  for easy recognition.


  AVAILABLE COMMANDS
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  As previously mentioned, the commands used by ViaSERV! are:

  SUB   - (or SUBSCRIBE) refers to the activation of a echomail conference
          or filebone area allowing the flow of mail/files for that area.

  UNSUB - (or UNSUBSCRIBE) performs the exact opposite action.  Disables
          the flow of mail/files for that area.

  GET   - Refers to having ViaSERV! collect information and return the
          results in the response message.

  SET   - Used to toggle the various settings either on, off or to some
          valid value.

  Each of these commands requires the use of parameters in order for it to
  function properly.  The format of these parameters will vary depending on
  it's usage and it explained below.


  SET COMMANDS
  ÄÄÄÄÄÄÄÄÄÄÄÄ

  SET ARCFORMAT <format>

  This command allows you to define the compression format that should be
  used when echomail is bundled up for your system.  A common usage might
  be:

                             SET ARCFORMAT ZIP

  The compression method (in this case ZIP) must be one of the available
  formats supported by the system.  Selecting an invalid format results in
  a listing of available formats in the response message.


  SET ECHOACTIVE <YES|NO>

  This command allows you to temporarily turn on or off the flow of
  echomail.  For example:

                              SET ECHOACTIVE NO

  would turn off the flow of mail while replacing the NO with YES would
  turn it back on again.  This option is handy should you be away from your
  system for an extended period of time.  Once you return, reactivating
  your system via the SET ECHOACTIVE YES command would start the flow of
  mail again.


  SET FILEACTIVE <YES|NO>

  This command functions exactly the same as SET ECHOACTIVE except that it
  controls the flow of TIC files.


  SET SERVPSWD <pswd>

  This command allows you to specify the password that should be used on
  the subject line of the message addressed to ECHOSERV or ARCSERV.  A
  common usage might be:

                              SET SERVPSWD happy

  This would change the current password to 'happy'.  You should note that
  while the password is in lowercase, when passwords are actually checked,
  upper/lower case becomes insignificant.


  SET SESSPSWD <pswd>

  This command allows you to define what your session password should be
  when calling this system.

                              SET SESSPSWD mail

  This password is used by the mailer when a remote system is calling and a
  secure session is required.


  SET INPKTPSWD <pswd>

  This command allows you to specify what should be expected by your uplink
  system at the password on echomail PKT files that your system sends to
  them.  A typical usage might be:

                             SET INPKTPSWD nice

  Once a password is established, all echomail from your system MUST have
  this password on it, otherwise it will be rejected.  If you would like to
  remove the password, simply use:

                             SET INPKTPSWD

  You should otice that no password has been defined.


  SET OUTPKTPSWD <pswd>

  This command functions nearly identically to it's counter part INPKTPSWD
  with the exception being that this is the password that will be put on
  echomail PKT files set TO your system from your uplink.  For example:

                           SET OUTPKTPSWD good

  Upon setting this password, you should to verify that this password
  matches what you have configured for your uplinks system in your echomail
  tosser.  The same method applies to removing the password as with the
  INPKTPSWD command.


  SET PKTFORMAT <format>

  This command allows you to specify the format used when echomail is added
  to PKT files destined for your system.  Current types are TYPE2, TYPE22
  and TYPE2+.  A common usage might be:

                           SET PKTFORMAT TYPE2+

  Normally this option would be set to TYPE2+, however you may change it
  as needed.  A special note for 'point' systems.  If you're a point off of
  your boss node, you will not be able to select TYPE2 as your PKT type.
  This is due in part to the inability of a TYPE2 PKT to correctly support
  a point address.  In that case, simply use TYPE22 or TYPE2+.


  SET UNCOMPSIZE <bytes>

  This command allows you to specify the total uncompressed bytes of
  echomail messages is allowable before a new archive gets created.  Common
  usage might be:

                          SET UNCOMPSIZE 2000000

  The value (in bytes) should be a conservative number taking into account
  the amount of free disk space on your system and the 'affordability' of
  losing a archive should it become corrupted.  A common value here would
  be 2,000,000.


  SYSTEM INFORMATION
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
  The following SET commands control the user specific information about
  your system.

            SET SYSOPNAME <name>          SET BBSNAME <name>
            SET MAILADDR1 <part 1>        SET MAILADDR2 <part 2>
            SET CITY <name>               SET STATE <state>
            SET ZIPCODE <zipcode>         SET VOICEPHONE <number>
            SET DATAPHONE <number>

  As with all the SET commands, these require the same 'third' parameter
  which replaces the existing information by what is specified.


  GET COMMANDS
  ÄÄÄÄÄÄÄÄÄÄÄÄ

  GET HELP

  This command will cause the entire contents of the information to be sent
  to you in the response mesage.  A common usage would be:

                              GET HELP

  You might consider using this command if you have trouble obtaining the
  information and/or results you're looking for.


  GET LIST

  This command will create a complete list of all the echomail conferences
  (or filebone areas) you currently have access to.  A common usage would
  be:

                               GET LIST

  This list will be sent back to you in the response message.  Depending on
  your uplinks configuration, this list could be quite large, so the
  response message(s) will be split accordingly.


  GET QUERY

  This command will create a list of all the echomail conferences (or
  filebone areas) your system is currently selected for.  A common usage
  would be:

                                GET QUERY

  This list will then be sent back to you in the response message.  Since
  this list could be quite large, the response message(s) will be split
  accordingly.


  GET UNLINKED

  This command is the counterpart to the GET QUERY command.  Instead of
  showing you all the selected areas, it will show you all of the echomail
  areas (or filebone areas) you have access to excluding the ones you're
  allready selected for.  A common usage would be:

                                GET UNLINKED

  This command is handy when you would like a list of areas that are still
  available for you to 'turn on'.


  GET STATUS

  This command will create a list of all the current settings your system
  is configured for and send it back to you in the response message.  A
  common usage would be:

                                GET STATUS

  This command is handy when you'd like to review your current
  configuration prior to making changes.


  GET RESCAN <conf> <num>

  This command allows you to extract the last <num> messages from the
  specified conference <conf> on your uplinks systems.  A typical usage
  might be:

                          GET RESCAN FOR-SALE 100

  In the above example, the last 100 messages from the FOR-SALE echomail
  conference would be extracted and packed up for your system.  Since this
  option only applies to echomail messages, you will not able to use this
  command if the message is sent to ARCSERV.  There is one additional
  limitation of this command.

  Since this command is meant to extract messages from a particular message
  base, if your uplinks system only carried the specified conference as a
  'pass-thru', attempting to use this command will result in no messages
  sent back to your system.  This is because a pass-thru conference doesn't
  have an associated message base upon which to extract messages from.


  GET CONTACT

  This command will retrieve the contact information from your uplinks
  system and send it back to you in the response message.  A common usage
  would be:

                                GET CONTACT

  Since this information normally contains your uplinks phone number and
  mailing address, this information could be useful should you need to
  contact him/her to discuss certain issues.



  SIGNALING THE END OF COMMANDS
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  A special group of characters called a tear line should be placed after
  the last command to signal that no more commands should be interpreted.

  This tear line consists of three dashes (---) together starting on column
  1 of a blank line. Although the tear line is not required, it should be
  there as a matter of practice.  This is done in cause you'd like to
  enter some text after the commands and not have them interpreted.


  SAMPLE MESSAGE
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  Shown below is a sample message.


  [1]     15 Feb 96  19:24:32                                      Cost: 0
  By: Joe Martin, The Power Station BBS (1:161/123)
  To: ECHOSERV, (1:161/55)
  Re: Password
  St: Kill  Del/sent Local
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
  SUB FOR-SALE
  UNSUB WILDCAT

  GET RESCAN FOR-SALE 50
  GET RESCAN GAMING ALL
  GET RESCAN WOODWORKING 100

  GET QUERY
  SET UNCOMPSIZE 2000000
  SET ARCFORMAT ARJ

  ---
  Any text below this (tear) line will be ignored.

                               -End of Help-

                    C O N T A C T   I N F O R M A T I O N
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
        Via Software Inc.                   Hours: 9am-5pm PST
        26489 Ynez Road, Suite C227         Voice: 1-909-699-2215
        Temecula, CA 92591                  Data : 1-909-699-2217
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
  Inf: The requested conference was not active on our system and as a
       result, a special request has been generated to our uplink feed.
       Expect to see mail for this conference flowing shortly.
  Inf: The requested file area was not active on our system and as a
       result, a special request has been generated to our uplink feed.
       Expect to see files for this area flowing shortly.
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
                      H E L P   I N F O R M A T I O N
                            Revised: 05/06/96
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  This system uses a special command interpreter (called ViaSERV!) which
  allows you to send specially formatted netmail messages addressed to the
  appropriate server and upon validation of the command(s), perform
  changes to your configuration.  This process is completely automatic and
  requires little (if any) intervention on the local system administrators
  part.


  COMMAND SERVER
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  Presently two server names are used:

                     ECHOSERV - Echomail conferences
                     ARCSERV  - Filebone conferences

  Selecting the apropriate server name only affects the performance of the
  SUBSCRIBE and UNSUBSCRIBE commands.  For example, using ECHOSERV in the
  To: name field dictates that using either the SUB/UNSUB commands will
  only affect the echomail conferences.  Likewise, using ARCSERV will only
  affect your filebone or TIC file areas.

  Since a common command set is used, you may take advantage of the various
  SET and GET commands (such as changing passwords, compression methods
  etc) regardless of which server the message is actually addressed to.
  This greatly simplies things by preventing you from having to learn a
  second set of commands.


  SECURITY
  ÄÄÄÄÄÄÄÄ

  Due to the power of this capability, ViaSERV! employs built-in security
  methods preventing unauthorized systems from gaining access and altering
  your configuration.  Any attempts to activate options you don't have
  sufficient access to will produce a response message back to your system
  informing you of this.

  All security level definitions and configuration is handled at the
  uplinks system, so any changes with regard to security must be made
  directly by the uplinks SysOp.  If you have any questions in this regard,
  you should contact him/her directly.


  RESPONSE MESSAGE
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  For every message you send, you will receive a response back telling you
  what was the outcome of the commands used.  Not only is this useful to
  verify that changes took place, but issuing the various GET STATUS, GET
  QUERY commands, you can see what are the conferences selected, your
  configuration and so on.


  SPECIALLY FORMATTED NETMAIL MESSAGE
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  When defining this message there's two distinct sections to configure.
  The message header (to/from addressing etc) and the message body.

  The message header selects the appropriate command server (ECHOSERV or
  ARCSERV) as well as the associated AKA address. The message body is
  where all the commands are placed.

  As mentioned above, selecting the To: name as ECHOSERV means using the
  SUB/UNSUB commands only affect your echomail areas and the name ARCSERV
  will only change your filebone or TIC file areas.


  MESSAGE HEADER
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  When defining the message header, the 5 basic sections are described
  below.

  To: address    The netmail message should be addressed to your uplinks
                 primary or any one of his AKAs (alternate addresses).

  To: name       Either ECHOSERV or ARCSERV.

  From: address  The FROM: address of the message should be your address
                 that has access to the related functions this request
                 is being configured for.  In other words, you should use
                 your correct AKA address relative to the network you're
                 requesting conferences for.  You wouldn't want to use
                 your Fido address for conferences within WSNET, instead
                 you would use your WSNET address.

  From: name     Normally you would use your regular name here.  This
                 field is not used except for display purposes.

  Subject line   This is one of the most crucial definitions because here
                 is where you specify your password that will enable the
                 use of the ViaSERV! commands.


  MESSAGE BODY
  ÄÄÄÄÄÄÄÄÄÄÄÄ

  The message body portion of the Netmail message is where all the 'action'
  takes place.  Here you could use the various SET and GET type commands to
  perform the desired action.

  You should only use one SET or GET command per line along with it's
  apropriate parameters.  If you'd like to enter multiple commands, you may
  do so by using multiple lines (one command per line).

  Blank lines, that is, a line with no text on it as well as lines that
  start off with a ';' or '#' character (in position 1) will be ignored.
  You might structure your message this way to provide better formatting
  for easy recognition.


  AVAILABLE COMMANDS
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  As previously mentioned, the commands used by ViaSERV! are:

  SUB   - (or SUBSCRIBE) refers to the activation of a echomail conference
          or filebone area allowing the flow of mail/files for that area.

  UNSUB - (or UNSUBSCRIBE) performs the exact opposite action.  Disables
          the flow of mail/files for that area.

  GET   - Refers to having ViaSERV! collect information and return the
          results in the response message.

  SET   - Used to toggle the various settings either on, off or to some
          valid value.

  Each of these commands requires the use of parameters in order for it to
  function properly.  The format of these parameters will vary depending on
  it's usage and it explained below.


  SET COMMANDS
  ÄÄÄÄÄÄÄÄÄÄÄÄ

  SET ARCFORMAT <format>

  This command allows you to define the compression format that should be
  used when echomail is bundled up for your system.  A common usage might
  be:

                             SET ARCFORMAT ZIP

  The compression method (in this case ZIP) must be one of the available
  formats supported by the system.  Selecting an invalid format results in
  a listing of available formats in the response message.


  SET ECHOACTIVE <YES|NO>

  This command allows you to temporarily turn on or off the flow of
  echomail.  For example:

                              SET ECHOACTIVE NO

  would turn off the flow of mail while replacing the NO with YES would
  turn it back on again.  This option is handy should you be away from your
  system for an extended period of time.  Once you return, reactivating
  your system via the SET ECHOACTIVE YES command would start the flow of
  mail again.


  SET FILEACTIVE <YES|NO>

  This command functions exactly the same as SET ECHOACTIVE except that it
  controls the flow of TIC files.


  SET SERVPSWD <pswd>

  This command allows you to specify the password that should be used on
  the subject line of the message addressed to ECHOSERV or ARCSERV.  A
  common usage might be:

                              SET SERVPSWD happy

  This would change the current password to 'happy'.  You should note that
  while the password is in lowercase, when passwords are actually checked,
  upper/lower case becomes insignificant.


  SET SESSPSWD <pswd>

  This command allows you to define what your session password should be
  when calling this system.

                              SET SESSPSWD mail

  This password is used by the mailer when a remote system is calling and a
  secure session is required.


  SET INPKTPSWD <pswd>

  This command allows you to specify what should be expected by your uplink
  system at the password on echomail PKT files that your system sends to
  them.  A typical usage might be:

                             SET INPKTPSWD nice

  Once a password is established, all echomail from your system MUST have
  this password on it, otherwise it will be rejected.  If you would like to
  remove the password, simply use:

                             SET INPKTPSWD

  You should otice that no password has been defined.


  SET OUTPKTPSWD <pswd>

  This command functions nearly identically to it's counter part INPKTPSWD
  with the exception being that this is the password that will be put on
  echomail PKT files set TO your system from your uplink.  For example:

                           SET OUTPKTPSWD good

  Upon setting this password, you should to verify that this password
  matches what you have configured for your uplinks system in your echomail
  tosser.  The same method applies to removing the password as with the
  INPKTPSWD command.


  SET PKTFORMAT <format>

  This command allows you to specify the format used when echomail is added
  to PKT files destined for your system.  Current types are TYPE2, TYPE22
  and TYPE2+.  A common usage might be:

                           SET PKTFORMAT TYPE2+

  Normally this option would be set to TYPE2+, however you may change it
  as needed.  A special note for 'point' systems.  If you're a point off of
  your boss node, you will not be able to select TYPE2 as your PKT type.
  This is due in part to the inability of a TYPE2 PKT to correctly support
  a point address.  In that case, simply use TYPE22 or TYPE2+.


  SET UNCOMPSIZE <bytes>

  This command allows you to specify the total uncompressed bytes of
  echomail messages is allowable before a new archive gets created.  Common
  usage might be:

                          SET UNCOMPSIZE 2000000

  The value (in bytes) should be a conservative number taking into account
  the amount of free disk space on your system and the 'affordability' of
  losing a archive should it become corrupted.  A common value here would
  be 2,000,000.


  SYSTEM INFORMATION
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
  The following SET commands control the user specific information about
  your system.

            SET SYSOPNAME <name>          SET BBSNAME <name>
            SET MAILADDR1 <part 1>        SET MAILADDR2 <part 2>
            SET CITY <name>               SET STATE <state>
            SET ZIPCODE <zipcode>         SET VOICEPHONE <number>
            SET DATAPHONE <number>

  As with all the SET commands, these require the same 'third' parameter
  which replaces the existing information by what is specified.


  GET COMMANDS
  ÄÄÄÄÄÄÄÄÄÄÄÄ

  GET HELP

  This command will cause the entire contents of the information to be sent
  to you in the response mesage.  A common usage would be:

                              GET HELP

  You might consider using this command if you have trouble obtaining the
  information and/or results you're looking for.


  GET LIST

  This command will create a complete list of all the echomail conferences
  (or filebone areas) you currently have access to.  A common usage would
  be:

                               GET LIST

  This list will be sent back to you in the response message.  Depending on
  your uplinks configuration, this list could be quite large, so the
  response message(s) will be split accordingly.


  GET QUERY

  This command will create a list of all the echomail conferences (or
  filebone areas) your system is currently selected for.  A common usage
  would be:

                                GET QUERY

  This list will then be sent back to you in the response message.  Since
  this list could be quite large, the response message(s) will be split
  accordingly.


  GET UNLINKED

  This command is the counterpart to the GET QUERY command.  Instead of
  showing you all the selected areas, it will show you all of the echomail
  areas (or filebone areas) you have access to excluding the ones you're
  allready selected for.  A common usage would be:

                                GET UNLINKED

  This command is handy when you would like a list of areas that are still
  available for you to 'turn on'.


  GET STATUS

  This command will create a list of all the current settings your system
  is configured for and send it back to you in the response message.  A
  common usage would be:

                                GET STATUS

  This command is handy when you'd like to review your current
  configuration prior to making changes.


  GET RESCAN <conf> <num>

  This command allows you to extract the last <num> messages from the
  specified conference <conf> on your uplinks systems.  A typical usage
  might be:

                          GET RESCAN FOR-SALE 100

  In the above example, the last 100 messages from the FOR-SALE echomail
  conference would be extracted and packed up for your system.  Since this
  option only applies to echomail messages, you will not able to use this
  command if the message is sent to ARCSERV.  There is one additional
  limitation of this command.

  Since this command is meant to extract messages from a particular message
  base, if your uplinks system only carried the specified conference as a
  'pass-thru', attempting to use this command will result in no messages
  sent back to your system.  This is because a pass-thru conference doesn't
  have an associated message base upon which to extract messages from.


  GET CONTACT

  This command will retrieve the contact information from your uplinks
  system and send it back to you in the response message.  A common usage
  would be:

                                GET CONTACT

  Since this information normally contains your uplinks phone number and
  mailing address, this information could be useful should you need to
  contact him/her to discuss certain issues.



  SIGNALING THE END OF COMMANDS
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  A special group of characters called a tear line should be placed after
  the last command to signal that no more commands should be interpreted.

  This tear line consists of three dashes (---) together starting on column
  1 of a blank line. Although the tear line is not required, it should be
  there as a matter of practice.  This is done in cause you'd like to
  enter some text after the commands and not have them interpreted.


  SAMPLE MESSAGE
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

  Shown below is a sample message.


  [1]     15 Feb 96  19:24:32                                      Cost: 0
  By: Joe Martin, The ViaSoft Support BBS (92:105/8)
  To: ECHOSERV, (92:105/0)
  Re: Password
  St: Kill  Del/sent Local
  ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
  SUB FOR-SALE
  UNSUB WILDCAT

  GET RESCAN FOR-SALE 50
  GET RESCAN GAMING ALL
  GET RESCAN WOODWORKING 100

  GET QUERY
  SET UNCOMPSIZE 2000000
  SET ARCFORMAT ARJ

  ---
  Any text below this (tear) line will be ignored.

                               -End of Help-